Format consistency
| Characteristic Name: | Format consistency |
| Dimension: | Consistency |
| Description: | Data formats are consistently used |
| Granularity: | Element |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of inconsistent data formats reported in an attribute per thousand records |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Maintain consistent formats for data values across different data bases and different tables in the same database. | (1) Telephone number : Country code/Area code/number (2) Address : House number, Street, Suburb, Sate, Country |
| Maintain structural similarity or compatibility of entities and attributes across systems (databases/data sets) and across time. | (1) Customer record has the same structure in all systems which it is being used. |
| Maintain consistent and compatible encoding /decoding standards across different applications. | (1) ASCII, UTF-8, XML |
Validation Metric:
| How mature is the creation and implementation of the DQ rules to maintain format consistency |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| 1) Each class in a UK secondary school is allocated a class identifier; this consists of the 3 initials of the teacher plus a two digit year group number of the class. It is declared as AAA99 (3 Alpha characters and two numeric characters).
2) A new year 9 teacher, Sally Hearn (without a middle name) is appointed therefore there are only two initials. A decision must be made as to how to represent two initials or the rule will fail and the database will reject the class identifier of “SH09”. It is decided that an additional character “Z” will be added to pad the letters to 3: “SZH09”, however this could break the accuracy rule. A better solution would be to amend the database to accept 2 or 3 initials and 1 or 2 numbers. 3) In this scenario, the parent, a US Citizen, applying to a European school completes the Date of Birth (D.O.B) on the application form in the US date format, MM/DD/YYYY rather than the European DD/MM/YYYY format, causing the representation of days and months to be reversed. |
N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013. |
| if a data element is used to store the color of a person’s eyes, a value of TRUCK is invalid. A value of BROWN for my eye color would be valid but inaccurate, in that my real eye color is blue. | J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| A measure of the equivalence of information stored or used in various data stores, applications, and systems, and the processes for making data equivalent | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| The extent to which similar attributes or elements of an information object are consistently represented using the same structure, format, and precision. | STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733. |
Standards and regulatory compliance
| Characteristic Name: | Standards and regulatory compliance |
| Dimension: | Validity |
| Description: | All data processing activities should comply with the policies, procedures, standards, industry benchmark practices and all regulatory requirements that the organization is bound by |
| Granularity: | Information object |
| Implementation Type: | Process-based approach |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due non adherence of standards and regulations |
| The number of complaints received due to non adherence to standards and regulations |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Identify the policies, procedures, standards, benchmark practices and any regulatory requirements that an Information object is bound by | (1) Each person's compensation criteria must be determined in accordance with the Annuities Based on Retired or Retainer Pay law. |
| Ensure that all data processing activities are well defined and documented based on the policies, procedures, standards, benchmarks and regulatory requirements. | (1) Process of making a damage estimate is well defined based on industry benchmarks |
| Ensure that the application programs cater for standards and regulatory compliance | (1) A software program to make damage estimates which includes all benchmark data |
| Regularly monitor the data processing activities and identify the problems and inefficiencies so that the corrective and preventive actions can be taken. | (1) Frequent delays in time sheet approvals results in delayed payments |
| Signs should be standardised and universally used | (1) In the line efficiency report, low efficiency lines are indicated using a RED light while a green light indicates high efficiency |
| Relevant standard, procedures, policies and regulations should be communicated to the users effectively | (1) Providing a guidelines for signs |
| Ensure that proper conversion tables are maintained and used in converting attribute vales to different measurement bases. | (1) Metric conversion tables are used to convert lbs to kgs. |
Validation Metric:
| How mature is the process maintain the adherence to standards and regulations |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| The age at entry to a UK primary & junior school is captured on the form for school applications. This is entered into a database and checked that it is between 4 and 11. If it were captured on the form as 14 or N/A it would be rejected as invalid. | N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| A measure of the existence, completeness, quality, and documentation of data standards, data models, business rules, metadata, and reference data. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| The data element has a commonly agreed upon enterprise business definition and calculations. | B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation. |
| SIGNS AND OTHER Information-Bearing Mechanisms like Traffic Signals should be standardized and universally used across the broadest audience possible. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| Validity of data refers to data that has been collected in accordance with any rules or definitions that are applicable for that data. This will enable benchmarking between organisations and over time. | HIQA 2011. International Review of Data Quality Health Information and Quality Authority (HIQA), Ireland. http://www.hiqa.ie/press-release/2011-04-28-international-review-data-quality. |